Automatic physical access

ABSTRACT

Physical access to secure areas is automatically performed based on presence or detection of a wireless device. A unique identifier of a wireless cellular device, for example, may be pre-authorized for occupants, employees, and tenants of a building. Contractors and vendors may also have their wireless cellular devices pre-approved for access. When the wireless cellular device is detected by a network serving the secure area, its unique identifier may be compared to databases or lists of approved cellular devices. Physical access may thus be automatically granted, based on possession of a recognized cellular device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 15/951,217 filed Apr. 12, 2018, which is a continuation of U.S. application Ser. No. 14/666,356 filed Mar. 24, 2015 and since issued as U.S. Pat. No. 9,972,144. All sections of the aforementioned application(s) and/or patent(s) are incorporated herein by reference in their entirety.

BACKGROUND

Secure physical access is important to homes and businesses. Much money and time are devoted to reducing rogue, criminal entry into homes and businesses.

BRIEF DESCRIPTION OF THE DRAWINGS

The features, aspects, and advantages of the exemplary embodiments are understood when the following Detailed Description is read with reference to the accompanying drawings, wherein:

FIGS. 1-7 are simplified schematics illustrating an environment in which exemplary embodiments may be implemented;

FIGS. 8-10 are more detailed block diagrams illustrating the operating environment, according to exemplary embodiments;

FIGS. 11-12 are schematics illustrating a database of meetings, according to exemplary embodiments;

FIGS. 13-18 are schematics illustrating locational tracking, according to exemplary embodiments;

FIGS. 19-22 are schematics illustrating building services, according to exemplary embodiments;

FIG. 23 is a schematic illustrating elevator summons, according to exemplary embodiments;

FIGS. 24-25 are schematics further illustrating a database of calendars, according to exemplary embodiments;

FIGS. 26-29 are schematics illustrating historical network tracking, according to exemplary embodiments;

FIG. 30 is a schematic illustrating network tracking, according to exemplary embodiments;

FIG. 31 is a schematic illustrating an overall database scheme, according to exemplary embodiments;

FIG. 32 is a schematic illustrating cancelations, according to exemplary embodiments;

FIG. 33 is a schematic illustrating conferencing activities, according to exemplary embodiments;

FIGS. 34-35 are flowcharts illustrating an algorithm for access authorization, according to exemplary embodiments; and

FIGS. 36-37 depict still more operating environments for additional aspects of the exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings. The exemplary embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. These embodiments are provided so that this disclosure will be thorough and complete and will fully convey the exemplary embodiments to those of ordinary skill in the art. Moreover, all statements herein reciting embodiments, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating the exemplary embodiments. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes,” “comprises,” “including,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include wirelessly connected or coupled. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first device could be termed a second device, and, similarly, a second device could be termed a first device without departing from the teachings of the disclosure.

FIGS. 1-7 are simplified schematics illustrating an environment in which exemplary embodiments may be implemented. FIG. 1 illustrates a human user 20 in a lobby 22 of a building 24. The human user 20 may be an employee working within the building 24, or the human may be visiting someone within the building 24. The human user 20, in short, may be an employee, a visitor, a contractor, a tenant, or a guest requesting entry into the building 24. For simplicity, the human user 20 will mainly be described as a visitor. When the visitor 20 wishes to enter an elevator 26 and proceed into secure areas of the building 24, the visitor 20 usually must check-in with a security guard. Here, though, exemplary embodiments detect the wireless presence of the visitor's mobile device 30, such as her smartphone 32. That is, if the visitor's smartphone 32 is recognized, then exemplary embodiments may permit entry of the visitor 20 to the secure areas within the building 24. However, if the visitor's smartphone 32 is unrecognized, then exemplary embodiments may require more authentication credentials or additional measures, as later paragraphs will explain.

FIG. 2 illustrates wireless presence. When the visitor enters some area (such as the lobby 22 or other area of the building 24), the visitor's smartphone 32 may attempt to access a wireless network 40 serving the lobby 22. As the reader likely understands, many people carry a smartphone that interfaces with wireless networks. So, when the visitor's smartphone 32 enters the lobby 22, the smartphone 32 may establish wireless communication with the wireless network 40 serving the lobby 22. The smartphone 32, for example, may request access or permission to a local area wireless fidelity (or WI-FI®) network serving the lobby 22 or any other area.

A security server 42 may be consulted. Once the wireless network 40 detects the radio presence of the visitor's smartphone 32, the security server 42 may determine whether the visitor 20 is authorized for entry, based on the wireless presence of the visitor's smartphone 32. For example, the security server 42 may consult a database 44 of personnel. The database 44 of personnel may store names, addresses, and/or other information for personnel who are authorized to enter the secure area of the building 24. The database 44 of personnel, however, may be arranged according to mobile devices. That is, the database 44 of personnel may store database associations between different names or identities of people and different unique identifiers of their mobile devices. If an entry in the database 44 of personnel matches the unique identifier of the visitor's smartphone 32, then the corresponding visitor 20 is authorized to enter the building 24. Employees and tenants may thus quickly and easily enter the building 24, merely based on wireless recognition of their mobile devices 30.

FIG. 3 further illustrates secure access. If the smartphone 32 is not matched to the database 44 of personnel, the visitor may still be granted access for legitimate purposes. For example, the visitor may be a supplier or contractor attending a meeting within the building 24. When the wireless network 40 detects the frequency presence of the visitor's smartphone 32, the security server 42 may consult a database 46 of meetings. The database 46 of meetings stores different meetings that are scheduled or calendared within the building 24. Each meeting may have an associated list 48 of invitees who are authorized to attend the meeting. Each invitee, however, may be identified according to his or her mobile device 30. That is, each invitee may be identified by a unique cellular identifier associated with, or assigned to, their cellular mobile device (such as the smartphone 32). The database 46 of meetings may thus store database associations between different scheduled meetings and different unique identifiers of the invitees' mobile devices 30. If an entry in the database 46 of meetings matches the unique identifier of the visitor's smartphone 32, then the corresponding human visitor may be authorized for entry to attend the corresponding meeting. Supplier personnel, contractors, and other invitees may thus quickly and easily enter the building, based on wireless recognition of their smartphones 32.

FIG. 4 further illustrates the database 46 of meetings. Here invitees may be more limited in the dates and times of their access. As FIG. 4 illustrates, each meeting 50 may also be associated with a date 52, a start time 54, and a duration 56. Even though the visitor's smartphone 32 may be matched as an invitee to the meeting 50, the visitor may still be denied access. For example, when the visitor's smartphone 32 requests access to the wireless network 40, a current date and time 58 may be time stamped. If the current date and time 58 does not match the scheduled date 52 of the meeting 50, then entry may be denied. Furthermore, if the smartphone 32 requests wireless access (to the wireless network 40) too early or too late for the scheduled meeting 50, then entry may be denied. The scheduled meeting 50 may thus have a window 60 of arrival, before or after which the visitor may not enter. So, even though a supplier or contractor is authorized for entry, admittance may be limited to nearly the scheduled date 52 and start time 54 of the meeting 50. The user of the smartphone 32 may thus be authorized for physical entry, but exemplary embodiments may require that the user wait until the window 60 of arrival is satisfied. Similarly, when the meeting 50 ends (perhaps at a stop time calculated using the duration 56), the visitor's smartphone 32 may not linger. Exemplary embodiments may thus continue tracking the smartphone 32 (as later paragraphs will explain) during and after the meeting 50 to ensure the visitor does not afterwards linger too long. If the attending visitor lingers too long after the meeting 50, exemplary embodiments may deny exit from the building, as a security precaution.

FIG. 5 illustrates a database 70 of calendars. Here the visitor's smartphone 32 may be matched to an individual's electronic calendar 72. As the reader likely understands, many people maintain their electronic calendars in a central location (such as an enterprise server database). The database 70 of calendars, in other words, stores different electronic calendars for different users (such as the employees and/or tenants in the building 24). When the wireless network 40 detects the radio presence of the smartphone 32, the security server 42 may query the database 70 of calendars for the unique identifier of the smartphone 32. If a matching calendar entry is determined, then the smartphone 32 is calendared to meet an employee or tenant inside the building 24. Exemplary embodiment may thus authorize entry, based on wireless network recognition of the visitor's smartphone 32.

FIG. 6 illustrates notification. Once the security server 42 authorizes the visitor's smartphone 32, electronic notifications may be sent. The security server 42 may thus generate and send one or more electronic messages 80 to destination devices 82 associated with different destination addresses 84, thus alerting of the visitor's entry into the building 24. An employee, for example, may be alerted to the visitor's arrival. Other meeting invitees may also be notified, using the unique identifier assigned to their respective smartphones.

FIG. 7 illustrates entry. Once the security server 42 authorizes the visitor's smartphone 32, the corresponding visitor may enter the secure area. The security server 42 may thus generate an electronic entry instruction 86 to allow physical entry. The entry instruction 86 is then sent as packets of data to any destination device. FIG. 7 , for example, illustrates the entry instruction 86 routing to a network address assigned to a lock controller 88. The lock controller 88 manages an electronic lock 90 securing some door or gate. The entry instruction 86 instructs the lock controller 88 to activate or unlock the electronic lock 90, thus allowing the visitor to physically enter the building 24 and/or some floor within the building 22. The security server 42 may further instruct an elevator controller 92 to summon an elevator 94, thus lifting the visitor to some floor or level, as later paragraphs will explain. The security server 42 may also monitor or track the movement of the visitor's smartphone 32 to prevent frolic or unauthorized detours (as later paragraphs will also explain).

Exemplary embodiments thus synchronize entry with wireless detection. Wireless detection of any mobile device 30 may thus be used to authorize entry to secure areas. Even though FIGS. 1-7 primarily illustrate the visitor's smartphone 32, exemplary embodiments may utilize any wired or wireless device (as later paragraphs will explain). Indeed, badges, watches, and other wearable smart devices may be wirelessly detected to permit access. Integration with personnel directories and calendaring systems further defines permissible locations of visitors.

FIGS. 8-10 are more detailed block diagrams illustrating the operating environment, according to exemplary embodiments. FIG. 8 illustrates presence detection of the visitor's smartphone 32. When the smartphone 32 enters any area, the smartphone 32 may establish wireless communication with the wireless network 40 serving the area. The smartphone 32, for example, may request access or permission to a local area wireless fidelity (or WI-FI®) network, wide area cellular network, or any other network. The wireless network 40 may only recognize, or transmit/receive, using a particular frequency or band. The smartphone 32 may thus instruct its transceiver (not shown for simplicity) to wirelessly request access permission using the electromagnetic frequency band required by the wireless network 40.

The security server 42 may be notified. When the wireless network 40 detects the smartphone 32, exemplary embodiments may inform the security server 42. That is, the smartphone 32 may send an access request to an access device 100 serving the wireless network 40. FIG. 8 illustrates the access device 100 as a wireless router 102, which commonly serves many residential and business WI-FI® networks. However, the access device 100 may be any network interface to an access network, such as a gateway, cable modem, or DSL modem. Regardless, the smartphone 32 broadcasts a request that seeks access permission to the wireless network 40. When the access device 100 receives the access request, the access device 100 may send a packetized access notification 104 into a communications network 106 for routing and delivery to a network address associated with the security server 42. The wireless router 102, for example, may store or execute code or programming that forces or commands the access notification 104 when any device attempts to access the wireless network 40. The access notification 104 may thus alert the security server 42 to the radio frequency presence of the visitor's smartphone 32. The access notification 104 may further include information that uniquely identifies the smartphone 32, such as data representing a cellular identifier 110. While any alphanumeric combination may uniquely identify the smartphone 32, FIG. 8 illustrates the smartphone's cellular telephone number (or “CTN”) 112, International Mobile Subscriber Identity (or “IMSI”) 114, or Mobile Station International Subscriber Directory Number (“MSISDN”) 116. Whenever the mobile smartphone 32 sends messages or information, the smartphone 32 may include or self-report its CTN 112, IMSI 114, and/or its MSISDN 116.

The security server 42 may authorize the smartphone 32. The security server 42 has a processor 120 (e.g., “μP”), application specific integrated circuit (ASIC), or other component that executes a security algorithm 122 stored in a local memory 124. The security algorithm 122 instructs the processor 120 to perform operations, such as receiving and processing information received from a network interface to the communications network 106. The information may be received as packets of data according to a packet protocol (such as any of the Internet Protocols). The packets of data contain bits or bytes of data describing the contents, or payload, of a message. A header of each packet of data may contain routing information identifying an origination address and/or a destination address. The security algorithm 122, for example, may instruct the processor 120 to inspect the packetized access notification 104 for the cellular identifier 110 associated with the visitor's smartphone 32 requesting access to the wireless network 40.

FIG. 9 illustrates the database 44 of personnel. The database 44 of personnel may store names, addresses, images, and/or other information for personnel who are authorized to enter any area. For simplicity the database 44 of personnel is illustrated as a table 130 that electronically maps, relates, or associates different employees or tenants 132 to their corresponding personal information. For example, an entry may associate each person's name 134, address 136, and/or employee number 138 to the cellular identifier 110 associated with the person's personal wireless device (such as the smartphone 32 illustrated in FIGS. 1-8 ). FIG. 9 illustrates the cellular identifier 110 as the cellular telephone number (“CTN”) 112, the IMSI 114, and/or the MSISDN 116. Each person's wireless device, however, may be additionally or alternatively uniquely identified by a network address, a manufacturer's serial number, or any other alphanumeric combination. Moreover, the database 44 of personnel may further associate a digital image file 140 to the cellular identifier 110, thus allowing retrieval, recognition, and/or analysis of a facial image. The database 44 of personnel is illustrated as being locally stored in the memory 124 of the security server 42, but some or all of the database entries may be remotely maintained at some other server or location in the communications network (illustrated as reference numeral 106 in FIG. 8 ). While FIG. 9 only illustrates a few entries, in practice the database 44 of personnel may contain many entries for hundreds or thousands of people.

The security server 42 may query the database 44 of personnel. Returning to FIG. 8 , when the security server 42 receives the access notification 104, the security algorithm 122 causes the processor 120 to query for entries that match the query search term(s) detailed or described in the electronic access notification 104. If the database 44 of personnel contains a matching entry, then the security server 42 may authorize the smartphone 32 (and thus the corresponding user or visitor) to enter. The security server 42 thus recognizes the smartphone 32 as belonging to one of the personnel authorized to enter the building (illustrated as reference numeral 24 in FIGS. 1-7 ). As an example, if the CTN 112, the IMSI 114, and/or the MSISDN 116 matches an entry in the database 44 of personnel, then the security server 42 may conclude that the corresponding user of the smartphone 32 is authorized to enter.

FIG. 10 illustrates the entry instruction 86. When the visitor's smartphone 32 is recognized, the security server 42 may automatically authorize entry. The security algorithm 122 may thus instruct the processor 120 to generate the entry instruction 86 to allow physical entry. The entry instruction 86 may contain any information that confirms the smartphone 32 is authorized to enter the secure area. FIG. 10 illustrates the entry instruction 86 routing to the network address assigned to the lock controller 88. The entry instruction 86 instructs the lock controller 88 to activate or unlock the electronic lock 90. The security server 42 may thus unlock a door, gate, or turnstile that permits physical entry of the corresponding user of the smartphone 32. An employee or tenant thus enters based on the wireless recognition of the smartphone 32.

Exemplary embodiments thus present an elegant solution. In today's mobile environment, people may be uniquely identified by their mobile devices (such as the smartphone 32). Employees, tenants, and visitors may thus be personally identified merely by carrying their smartphones. Exemplary embodiments may thus permit authorized entry to secure areas, simply by recognizing wireless transmissions from their mobile devices. No phone calls are needed, and labor expenses are reduced.

Exemplary embodiments may be applied regardless of networking environment. Exemplary embodiments may be easily adapted to stationary or mobile devices having cellular, WI-FI®, near field, and/or BLUETOOTH® capability. Exemplary embodiments may be applied to mobile devices utilizing any portion of the electromagnetic spectrum and any signaling standard (such as the IEEE 802 family of standards, GSM/CDMA/TDMA or any cellular standard, and/or the ISM band). Exemplary embodiments, however, may be applied to any processor-controlled device operating in the radio-frequency domain and/or the Internet Protocol (IP) domain. Exemplary embodiments may be applied to any processor-controlled device utilizing a distributed computing network, such as the Internet (sometimes alternatively known as the “World Wide Web”), an intranet, a local-area network (LAN), and/or a wide-area network (WAN). Exemplary embodiments may be applied to any processor-controlled device utilizing power line technologies, in which signals are communicated via electrical wiring. Indeed, exemplary embodiments may be applied regardless of physical componentry, physical configuration, or communications standard(s).

Exemplary embodiments may utilize any processing component, configuration, or system. Any processor could be multiple processors, which could include distributed processors or parallel processors in a single machine or multiple machines. The processor can be used in supporting a virtual processing environment. The processor could include a state machine, application specific integrated circuit (ASIC), programmable gate array (PGA) including a Field PGA, or state machine. When any of the processors execute instructions to perform “operations”, this could include the processor performing the operations directly and/or facilitating, directing, or cooperating with another device or component to perform the operations.

FIGS. 11-12 are schematics further illustrating the database 46 of meetings, according to exemplary embodiments. Here the smartphone 32 may be an invitee to a meeting within some secure area. When the wireless network 40 detects the radio presence of the visitor's smartphone 32, the access device 100 sends the access notification 105 to the security server 42. The packetized access notification 104 may include data describing the cellular identifier 110 (e.g., the CTN 112, the IMSI 114, and/or the MSISDN 116). The security server 42 may then query the database 46 of meetings to determine if the smartphone 32 matches the list 48 of invitees to any scheduled meeting 50.

FIG. 12 illustrates the database 46 of meetings. For simplicity, FIG. 12 illustrates the database 46 of meetings being locally stored in the memory 124 of the security server 42. However, some or all of the database entries may be remotely maintained at some other server or location in the communications network (illustrated as reference numeral 106 in FIG. 11 ). While FIG. 12 only illustrates a few entries, in practice the database 46 of meetings may contain many entries for hundreds or thousands of different meetings or gatherings. The database 46 of meetings is illustrated as a table 150 that maps, relates, or associates different scheduled meetings 50 to the corresponding list 48 of invitees. While each invitee 48 may be identified by their name, here exemplary embodiments identify each invitee 48 according to his or her mobile device identifier. That is, each invitee 48 may be identified by the unique cellular identifier 110 associated with, or assigned to, their cellular device (such as the smartphone 32). FIG. 12 thus illustrates database associations between a meeting 50, an organizer or inviter 152, and the different invitees 48. Each party to the meeting 50 may thus be uniquely identified by their respective CTN 112, IMSI 114, and/or MSISDN 116. Referring back to FIG. 11 , if an entry in the database 46 of meetings matches the unique cellular identifier 110 associated with the smartphone 32, then the corresponding user may be authorized for entry to attend the corresponding meeting 50. The security server 42 may thus authorize entry, such as by generating the entry instruction 86 (as illustrated with reference to FIG. 10 ). Supplier personnel, contractors, and other invitees may thus quickly and easily enter the building, based on wireless recognition of their smartphones.

FIGS. 13-18 are schematics illustrating locational tracking, according to exemplary embodiments. Once the smartphone 32 is authorized for entry, exemplary embodiments may monitor the movements of the smartphone 32. If the visitor's smartphone 32 strays or frolics, a security concern may develop. Exemplary embodiments, then, may track the smartphone 32 to ensure the user stays on route to the meeting 50.

FIG. 13 , for example, illustrates room assignments. Here the database 46 of meetings may also associate a meeting location 154 to each meeting 50. As the reader may realize, conference rooms, offices, beverage rooms, and auditoriums may be uniquely identified by some name and/or location. So, when the meeting 50 is scheduled or logged in the database 46 of meetings, exemplary embodiments may further store an electronic database association with the corresponding meeting location 154.

FIG. 14 illustrates security routings. Once the location 154 of the meeting 50 is determined (from the database 46 of meetings), the security server 42 may query a database 160 of routings. The database 160 of routings stores predetermined building routes 162 from some beginning location (such as a point of entry 164) to the destination at the meeting location 154. The database 160 of routings, for example, may store different routes 162 from the lobby of the building (illustrated, respectively, as reference numerals 22 and 24 in FIG. 1 ) to the meeting location 154 of the scheduled meeting 50. FIG. 14 illustrates the database 160 of routings as being locally stored in the security server 42, but some or all of the electronic database entries may be remotely maintained at some other server or location in the communications network (illustrated as reference numeral 106 in FIG. 11 ). A particular conference room, for example, may have a route 162 along which the visitor is only permitted to walk or navigate. That is, only certain paths along particular halls and/or through particular doors are available to the visitor. The database 160 of routings may thus store approved routes 162 along which employees, tenants, and/or visitors may move from any point (such as the entry 164) to the final destination at the meeting location 154.

FIG. 15 illustrates GPS tracking. After the visitor's smartphone 32 is authorized for entry, the visitor should walk or travel along the predetermined route 162 to the destination meeting location 154. After all, confining the visitor to the predetermined route 162 may help prevent rogue access to unauthorized locations. Exemplary embodiments, then, may track the visitor's position or progress along the predetermined route 162. FIG. 15 thus illustrates GPS waypoints 170 along which the smartphone 32 may or must report. That is, the predetermined route 162 may be defined as a series of global positioning system information. As the visitor walks the corridors of the building, the visitor's smartphone 32 may continually, periodically, and/or randomly report its current location 172. FIG. 15 illustrates the smartphone 32 reporting its current location 172 into the wireless network 40, which the access device 100 may forward to the security server 42. The current location 172, however, may be routed into a cellular network for delivery to the network address associated with the security server 42. Regardless, when the security server 42 receives the current location 172, the security server 42 may compare the current location 172 to the GPS waypoints 170 associated with the meeting location 154. If the current location 172 matches one of the GPS waypoints (perhaps within a locational tolerance), then the security algorithm 122 may conclude that the visitor's smartphone 32 is on track and proceeding as authorized. However, if the current location 172 reported by the visitor's smartphone 32 fails to match one or any of the GPS waypoints 170, the security algorithm 122 may generate a security notification 174. The security notification 174 may be any electronic message that warns the visitor to resume the predetermined route 162 to the destination meeting location 154. The security notification 174 may route back to the access device 100 for transmission to the network address assigned to the smartphone 32. However, the security notification 174 may be a short message service (SMS) text message that is sent to the unique cellular identifier 110 of the visitor's smartphone 32. The security notification 174 may further include a correction 176 that puts the visitor back on the predetermined route 162 to the destination meeting location 154. Moreover, the security server 42 may also copy or forward the security notification 174 to a device associated with a security guard for nearly immediate human intervention.

FIG. 16 illustrates network tracking. Here exemplary embodiments may infer the location of the visitor's smartphone 32 using network recognition. As the reader may understand, GPS signals are sometimes not received in indoor environments. Exemplary embodiments, then, may additionally or alternatively infer the location of the visitor's smartphone 32 using network identifiers. FIG. 16 thus illustrates network waypoints 180 along which the smartphone 32 must request access permission. That is, the predetermined route 162 may be defined as a series of network identifiers. For example, as the visitor walks the corridors of the building, the visitor's smartphone 32 may wirelessly encounter different wireless fidelity (WI-FI®) networks serving the different floors, hallways, and/or rooms. The visitor's smartphone 32 may also detect other identifiers of other networks (such as different cellular network cells). Regardless, the smartphone 32 may request access permission to each wireless network 40. The corresponding access device 100 may thus notify the security server 42 using the access notification 104 (above explained with reference to FIG. 8 ). FIG. 16 , for simplicity, illustrates the network waypoints 180 as a series 182 of service set identifiers. Each individual service set identifier (or “SSID”) 184 uniquely identifiers a different WI-FI® network serving some portion of the predetermined route 162 to the destination meeting location 154. When the security server 42 receives each access notification 104, the access notification 104 may identify the corresponding SSID 184. The security server 42 may thus compare the SSID 184 to the network waypoints 180 associated with the meeting location 154. If the SSID 184 matches one of the network waypoints 180, then the security algorithm 122 may conclude that the visitor's smartphone 32 is on track and proceeding as authorized. However, if the SSID 184 fails to match one or any of the network waypoints 180, the security algorithm 122 may generate the security notification 174 with the correction 176 (as earlier explained).

FIG. 17 illustrates a strict comparison. As the security server 42 receives each access notification 104, the security server 42 may require a strict sequential match with the network waypoints 180. The visitor's smartphone 32, in other words, may be required to traverse the network waypoints 180 in sequential order, from a first entry SSID 190 to a final destination SSID 192 serving the destination meeting location 154. If the visitor's smartphone 32 strays from the predetermined route 162, one of the access notifications 184 will identify an SSID 184 not matching the approved route 162. The smartphone 32, in other words, is requesting wireless access to an unauthorized network, thus revealing a frolic or detour. The security algorithm 122 may thus alert security (as earlier explained).

FIG. 18 illustrates timing requirements. Here each network waypoint 180 may also have a corresponding timing parameter 200. FIG. 18 thus illustrates each network waypoint 180 as an SSID/time pairing. That is, each network waypoint 180 may be a network/timing pair of values associated with each successive wireless network 40. As the visitor's smartphone 32 travels along the predetermined route 162, the security server 42 may monitor a speed or time of movement. Each access notification 104 may have a timestamp 202 that marks a time of requested access to the wireless network 40 (as identified by the SSID 184). As the security server 42 sequentially compares the SSID 184 to the network waypoints 180, the security server 42 may also require strict adherence to each corresponding timing parameter 200. The security server 42, in other words, may initialize a timer 204 with receipt of the access notification 104. The timer 204 counts up or down to a final value at a receipt of a next access notification 104 associated with the same smartphone 32 (e.g., the cellular identifier 110). The timer 204, for example, may thus count a time in seconds or minutes between successive access notifications 104 sent from different access devices 100 along the predetermined route 162. So, not only must each sequential SSID 184 match the network waypoints 180, but exemplary embodiments may also require timing compliance between the successive network waypoints 180. The security server 42 may thus compare a current value of the timer 204 to the timing parameter 200 associated with a next corresponding network waypoint 182 along the predetermined route 162. If the current value of the timer 204 is less than or equal to the timing parameter 200, then the security algorithm 122 may conclude that the visitor's smartphone 32 is on the approved route 162 and on track to arrive on time at the final meeting destination location 154. However, if the current value of the timer 204 exceeds the timing parameter 200, the security algorithm 122 may conclude that the visitor's smartphone 32 has strayed from the predetermined route 162. The security algorithm 122 may thus alert security (as earlier explained).

FIGS. 19-22 are schematics illustrating building services, according to exemplary embodiments. Here exemplary embodiments may coordinate or time various building services with respect to the location of the smartphone 32. As the smartphone 32 travels along the predetermined route 162 (as represented by the GPS current location 172, any of the GPS waypoints 170, the SSID 184, and/or any of the network waypoints 180), the security server 42 may thus order up or coordinate various building services at appropriate times and locations. FIG. 19 , for example, illustrates a database 210 of services. The database 210 of services is illustrated as a table 212 that associates different locations 214 to different services 216. As the reader may understand, one of the services 216 may be lighting requirements 218 for each different location 214. As the user carries the smartphone 32 through hallways and other areas, lights may need to be activated. So, as the security server 42 is informed of the smartphone's location 214 along the route 162, the security server 42 may query the database 210 of services for the corresponding lighting requirements 218.

Lights may thus be defined. The database 210 of services may thus store electronic database associations for the lights that illuminate the different locations 214. Each wireless network 40, for example, may be mapped to the light fixtures 220 and/or lighting loads 222 (such as individual electrical circuits) illuminating its wireless service area. Whenever the security server 42 receives the access notification 104, the security server 42 may thus query for the SSID 184 and retrieve the lighting requirements 218 for its wireless service area. As FIG. 19 further illustrates, electronic database associations may be defined for any GPS coordinates or waypoints along the route 162.

As FIG. 20 illustrates, the lights may be activated. Once the security server 42 knows the lighting requirements 218 for the location 214, the security server 42 may send a lighting command 230 into the communications network 106 for delivery to the network address associated with a lighting controller 232. The lighting controller 232 responds by activating, or turning on, the corresponding physical light fixture 234 and/or the physical electrical load 236. The security server 42 may thus coordinate the lights along the predetermined route 162 for safety and security. Lights may then be deactivated when no mobile device requests wireless access to the corresponding wireless service area. Lights may also be deactivated after some passage of time.

FIG. 21 illustrates HVAC services. Here exemplary embodiments may also coordinate heat or air conditioning with respect to the location 214 along the approved route 162. As the reader likely understands, as the user or visitor travels along the predetermined route 162 (as represented by the GPS current location 172, any of the GPS waypoints 170, the SSID 184, and/or any of the network waypoints 180), the security server 42 may heat or cool the corresponding physical space or area. Indeed, the security server 42 may even order up an ambient temperature within the destination meeting location (illustrated as reference numeral 154 in FIGS. 15-16 ). The database 210 of services may thus include entries for HVAC settings 240 associated with the location 214 along the approved route 162. For example, the security server 42 may thus query the database 210 of services for the SSID 184 and retrieve the corresponding HVAC settings 240 (such as a temperature 242 and/or humidity 244) associated with the corresponding physical space or area. The security server 42 may then send an HVAC command 246 into the communications network 106 for delivery to the network address associated with an HVAC system 248. The security server 42 may even receive weather data 249 to further analyze and satisfy the HVAC settings 240 desired for the corresponding physical space or area.

FIG. 22 illustrates other services. Exemplary embodiments may also coordinate many other services for the comfort and convenience of the invitees/attendees. The database 210 of services, for example, may also have entries for other services, such as network access 250, equipment 252, and vending 254. Continuing with the above examples, the security server 42 may query the database 210 of services for the SSID 184 of the meeting location 154. The security server 42 may thus retrieve the corresponding services 216 defined for that meeting location 214. The security server 42 may then generate an electronic, packetized service order 256 that routes to a network address of a service provider system 258. For example, when each invitee arrives at the destination meeting location 154, the security server 42 may arrange or prearrange wireless network access 250 for each attendee's mobile wireless device. The security server 42, for example, knows the SSID 184 of the WI-FI® network serving the destination conference room, along with the unique cellular identifier 110 of each attendee's wireless device (as explained with reference to FIGS. 11-14 ). The security server 42 may thus pre-authorize each attendee's wireless device for wireless service in the destination conference room. Any wireless access point, in other words, may be instructed to recognize the unique cellular identifier 110 of each attendee's wireless device. Each attendee's device thus has immediate access to wireless services.

The equipment 252 may also be ordered. Computers, projectors, conference phone set-up, pens, and whiteboards are just some of the equipment 252 that may be pre-ordered, based on the location 214. The meeting organizer (illustrated as reference numeral 152 in FIG. 12 ) may thus enter any data or description of the equipment 252 desired for the meeting. The security server 42 may thus pre-arrange arrival and set-up of the equipment 252. As the attendees enter the destination meeting location 154, the equipment 252 they need is automatically ordered and waiting for use.

Vending 254 may also be pre-arranged. The meeting organizer may thus enter or request any food and drink for the meeting. The security server 42 may thus issue orders or commands for on-time delivery of food and drink from some identified vendor. As the attendees enter the destination meeting location 154, the requested food and drink is automatically ordered and waiting for consumption.

FIG. 23 is a schematic illustrating elevator summons, according to exemplary embodiments. As the smartphone 32 moves along the pre-approved route 162 to the destination meeting location 154, at some point elevator service may be required. Exemplary embodiments may thus track the smartphone's movement and generate elevator commands at appropriate moments in time or location. FIG. 23 , for example, illustrates an elevator command 270 as a data triplet 271 inserted into one of the network waypoints 180. The elevator command 270 identifies which elevator (elevator number or identifier) is summoned for vertical travel from an entry floor to an exit floor. If a building only has one elevator, then perhaps the elevator command 270 may be simplified to a pair of data values. But many buildings may have multiple elevators, perhaps serving different floors. The elevator command (3, 1, 22), for example, may call or summon “Elevator #3” to “Floor #1” for lift service to “Floor #22.” The opposite elevator command (3, 22, 1) would call “Elevator #3” to “Floor #22” for descend service to “Floor #1.” Each elevator command 270 may thus be generated for insertion into the pre-determined sequential network waypoints 180. As the smartphone 32 satisfied each sequential network waypoint 180, the security server 42 may summon the corresponding elevator in the sequence. The security algorithm 122 may further initialize the timer 204 to count up or down until the summons. Exemplary embodiments, then, may insert the elevator command 270 at appropriate positions and/or times in the sequential network waypoints 180 and/or the sequential GPS waypoints (illustrated as reference numeral 170 in FIG. 15 ). As the security server 42 tracks the smartphone 32, the security server 42 may thus read, retrieve, and/or execute the elevator command 270 as one of the sequential steps. The security server 42 may thus generate an elevator instruction 272 that is sent into the communications network 106 for delivery to the network address associated with the elevator controller 92. Elevator service may thus be summoned to coincide with the current location of the smartphone 32.

FIGS. 24-25 are schematics further illustrating the database 70 of calendars, according to exemplary embodiments. When the wireless network 40 detects the radio presence of the visitor's smartphone 32, the access device 100 sends the access notification 104 (as earlier explained). The security server 42 may then query the database 70 of calendars for a matching entry. The database 70 of calendars stores different electronic calendars for the different employees and/or tenants in the building. FIG. 25 , for example, illustrates the database 70 of calendars as a table 280 that maps, relates, or associates different electronic calendars 72 to different invitees 282. As there may be hundreds of employees or tenants, the database 70 of calendars may store a memory pointer or network address to an individual person's electronic calendar 72. Regardless, when the visitor's smartphone 32 requests access to the wireless network 40, the database 70 of calendars may be searched or queried for a matching entry. For example, FIG. 25 illustrates the database 70 of calendars storing electronic database associations between electronic calendar entries 72 and their respective invitees 282. Whenever a person schedules a meeting or telephone call, for example, the invitee may be uniquely identified by his or her unique cellular identifier 110. An appointment in an electronic calendar, in other words, may be arranged or associated with the CTN 112, the IMSI 114, and/or the MSISDN 116 of a participant 282.

The security server 42 may authorize entry. Referring back to FIG. 24 , when the security server 42 receives the access notification 104, the security server 42 may query the database 70 of calendars for the visitor's unique cellular identifier 110. If a matching entry is determined, the security server 42 may permit physical entry, as the visitor is scheduled for an appointment with an employee or tenant. Moreover, if the database 70 of calendars identifies the meeting location 154, the security server 42 may further retrieve and monitor the predetermine route 162 to the meeting location 154 (as this disclosure explains with reference to FIGS. 14-18 and 23 ).

FIGS. 26-29 are schematics illustrating historical network tracking, according to exemplary embodiments. Here, historical observances of wireless detections may be used to infer future actions. That is, a user's habitual usage of the smartphone 32 may be used to predict where she will move, and/or what she will do, based on her past movements and wireless network access. For example, as the smartphone 32 repeatedly moves within the building 24, over time exemplary embodiments may make recommendations and assumptions, based on habitual observance of its network usage. Whenever the smartphone 32 is detected at some location or requesting access to any network, exemplary embodiments may match that detection to some past occurrence. In other words, most people are creatures of habit, so exemplary embodiments may predict our future movements and actions based on our historical behaviors.

FIG. 26 illustrates a database 300 of usage. The database 300 of usage tracks historical usage of any user's wireless device 30 (such as the smartphone 32). The database 300 of usage may store entries related to usage at different times of days and/or at different locations. Whenever the smartphone 32 reports its GPS current location 172, for example, exemplary embodiments may query the database 300 of usage for historical usage at that same location. The database 300 of usage may thus log each current location 172 reported by the smartphone 32. As the smartphone 32 moves within the building 24, the smartphone 32 may repeatedly send its current location 172 (such as GPS information) to the security server 42. The security server 42 may then log these locational reports in the database 300 of usage. The database 300 of usage is illustrated as being locally stored within the security server 42, but any of the database entries may be remotely maintained at other network-accessible locations or servers. FIG. 26 illustrates the database 300 of usage as a table 302 that electronically maps, relates, or associates the cellular identifier 110 to different location reports. That is, each time the smartphone 32 reports its current location 172, the database 300 of usage may add an entry for the unique cellular identifier 110, the reported current location 172, and a date and time 304 of the report. Over time, then, the database 300 of usage may store long-term records of the movements of the smartphone 32 within the building 24.

FIG. 27 illustrates historical network usage. Each time the smartphone 32 requests access to the wireless network 40, the corresponding access device 100 sends the packetized access notification 104 to alert the security server 42 (as this disclosure earlier explained). The security server 42 may thus instruct the database 300 of usage to log the access notification 104, perhaps also with the date and time 304. That is, each time the smartphone 32 requests wireless access to the wireless network 40, the database 300 of usage may add an entry for the unique cellular identifier 110, the service set identifier (“SSID”) 184 of the wireless fidelity (“WI-FI®”) network 40, and the date and time 304 of the request. As FIG. 27 illustrates, the database 300 of usage may merely log the timestamp 202 reported in the access notification 104, or the database 300 of usage may log some other measure of time (such as receipt of the access notification 104). Regardless, over time the database 300 of usage reveals a comprehensive long-term central repository of network access requested by the smartphone 32.

The security server 42 may thus infer future entries from the historical information. The security server 42, for example, may query the database 300 of usage for any search terms and retrieve matching historical entries. The security server 42, as an example, may query for historical entries associated with the cellular identifier 110. The security server 42 may thus retrieve historical locations or networks logged in the database 300 of usage. Indeed, the security server 42 may even query for historical entries having the same or approximate date and time 304. The security server 42 may thus retrieve historical entries that match the same or similar day, time, current location 172, or network SSID 184.

FIG. 28 illustrates locational prediction. Whenever the smartphone 32 reports its current location 172, the security server 42 may predict or infer a future location 310. For example, the security server 42 may query for a series or sequence of entries having about the same location 172 and/or the same date and time 304. For example, if one or more of the smartphone's recent locational reports match one or more historical entries, then the security algorithm 122 may infer that the smartphone 32 is moving along a path historically observed. That is, the smartphone 32 is being carried along a familiar route to a historical destination previously logged in the database 300 of usage. In other words, if a recent string or sequence of locational reports matches some sequence of historical entries, then the security algorithm 122 may conclude that the smartphone 32 is traveling along the same route to the same destination. If the smartphone 32 reports the same current locations 172 within a ten minute (10 min.) window of time as historically seen, the security server 42 may thus predict or infer that the smartphone 32 will have the future location 310 that matches at least one of the historical entries in the same series. As one example, if the smartphone's most recent five (5) location reports match some historical observance in the database 300 of usage, then the security server 42 may predict the smartphone's future location 310 will match the next historical sixth (6^(th)) entry in the same historical sequence. The security server 42 may thus query for any search terms and retrieve one or multiple historical entries that match recent locational reports. As most people are creatures of habit, the security server 42 may thus predict the future location 310 of the smartphone 32 based on historical observances.

FIG. 29 illustrates network prediction. As the database 300 of usage may also log historical network requests, exemplary embodiments may predict or infer a future network 312. For example, the security algorithm 122 may predict the smartphone's access request to a wireless fidelity (“WI-FI®”) network, based on the historical entries in the database 300 of usage. The security server 42 may query for a series or sequence of entries having one or more matching SSID 184 entries and/or about the same date and time 304. For example, if one or more of the recent access notifications 104 match one or more historical entries, then the security algorithm 122 may infer that the smartphone 32 is requesting access permissions along a path historically observed. In other words, if a recent string or sequence of access notifications 104 matches some sequence of historical entries, then the security algorithm 122 may conclude that the smartphone 32 is requesting wireless access as historically seen. If a string or sequence 314 of the access notifications 104 match historical entries within a ten minute (10 min.) window 316 of time, the security server 42 may thus predict or infer that the smartphone 32 will request access to a next entry historically observed in the same series. As FIG. 29 illustrates, if the recent access notifications 104 report the sequence 314 “SSID2, SSID3, SSID4, SSID3,” then the security algorithm 122 may retrieve the next entry in the same sequence 314 and predict that the smartphone 32 will next request access to “SSID9.” The security algorithm 122, in other words, infers the future network 312 as the next entry in the matching sequence 314. The security algorithm 122 may thus pre-arrange wireless access, elevator service, lighting, and other services based on this prediction.

FIG. 30 is another schematic illustrating network tracking, according to exemplary embodiments. Here exemplary embodiments may track usage or access requests to any networking environment. As FIG. 30 illustrates, whenever the smartphone 32 requests access to any wireless network 40, the access notification 104 may report the networking details. The access notification 104, for example, may report a radio frequency 320 and/or bitrate 322 of communication between the smartphone 32 and some other device (such as the access device 100). The timestamp 202 may be further added. When the security server 42 receives the access notification 104, the security algorithm 122 may thus log these details in the database 300 of usage. For example, the radio frequency 320 and/or bitrate 322 may allow the security algorithm 122 to log whether the wireless network 40 operates at cellular frequencies or WI-FI® frequencies.

Other networking environments may also be tracked. When the security server 42 receives the access notification 104, the radio frequency 320 and/or the bitrate 322 may reveal near-field communications (“NFC”) and/or radio frequency identification (“RFID”) communications. For example, when the smartphone 32 participates in near-field communication, the access notification 104 may additionally or alternatively report an initiator device 324 and a target device 326. Likewise, the access notification 104 may also detail unique radio frequency identification tags and readers. When the security server 42 receives the access notification 104, the security algorithm 122 may thus log these details in the database 300 of usage. Over time, then, the database 300 of usage contains historical entries detailing the NFC and RFID transactions involving the smartphone 32. If any current transaction matches some historical entry, the security algorithm 122 may predict or infer future actions and/or locations, based on the match. The security algorithm 122 may thus pre-arrange wireless access, elevator service, lighting, and other services based on this prediction.

FIG. 31 is a schematic illustrating an overall database scheme, according to exemplary embodiments. Here the security server 42 may access any of the databases (illustrated as reference numerals 44, 46, 70, 160, 210, and 300) to authorize access, to coordinate services, and to predict actions, as this disclosure explains. The databases may be individually maintained or grouped together, depending on networking, processing, and storage capabilities.

FIG. 32 is a schematic illustrating cancelations, according to exemplary embodiments. Even though the security server 42 may have authorized access, coordinated services, and/or predicted actions, sometimes cancelations are determined. For example, a meeting organizer may simply cancel a scheduled meeting in the database 46 of meetings. This cancelation 340 may then trickle down and affect access, services, and predictions. For example, if the cancelation 340 is determined in the database 46 of meetings, the security server 42 may disperse that cancelation 340. The invitees' devices to the now-canceled meeting may be notified (perhaps using the notification message 80 illustrated in FIG. 6 ). Entry authorization for the invitees' devices may be canceled by removal from the database 46 of meetings and/or removal from the database 70 of calendars. The entry instruction (illustrated as reference numeral 86 in FIG. 7 ) may be canceled, thus stopping or ceasing any entry process. The elevator instruction (illustrated as reference numeral 272 in FIG. 23 ) may be canceled, thus removing any summons for elevators. Likewise, any retrieval and/or analysis of routes in the database 160 of routings may be canceled or aborted. Any retrieval and/or electronic order of services in the database 210 of services may also be canceled or aborted. Moreover, electronic notifications of the cancelation 340 may be sent to service providers (such as contractors and vendors). Any historical analysis of entries in the database 300 of usage may be halted or aborted. The cancelation 340 may thus electronically cancel any reservation for a conference room, HVAC needs, and lighting requirements.

FIG. 33 is a schematic illustrating conferencing activities, according to exemplary embodiments. Here exemplary embodiments may arrange and set-up a teleconference call and/or a telepresence video call between the visitor's smartphone 32 and other participants. When the visitor arrives, the visitor's smartphone 32 requests wireless access (as earlier explained). The security server 42 may thus use the unique cellular identifier 110 to retrieve any meeting entries in the database 46 of meetings and/or in the database 70 of calendars. The security server 42 may arrange a conference room and/or an office or desk for the visitor, in response to a matching entry. The security server 42 may also automatically set-up a teleconference call or a videoconference call to the meeting invitee devices retrieved from the database 46 of meetings and/or the database 70 of calendars. The security server 42 may also concomitantly arrange video cameras, whiteboards, beverages, lighting, and other services (perhaps revealed by the database 210 of services, as previously explained).

FIGS. 34-35 are flowcharts illustrating an algorithm for access authorization, according to exemplary embodiments. A unique cellular identifier 110 is received (Block 350) and the security server 42 is notified (Block 352). A database is queried for the cellular identifier 110 (Block 354). Physical access to a secure area is granted, based on a matching entry in the database (Block 356). The electronic lock 90 may be activated to permit entry (Block 358). The electronic notification message 80 may be sent to a meeting organizer and/or other invitees, thus alerting to the arrival and access of the user associated with the cellular identifier (Block 360). The location 154 of the meeting may also be determined (Block 362).

The flowchart continues with FIG. 35 . Once the location 154 is known, the corresponding route 162 retrieved (Block 364). The elevator 94 may be summoned (Block 366). The corresponding services 216 may also be retrieved (Block 368). Historical usage associated with the cellular identifier 110 is retrieved (Block 370). The future location 310 (Block 372) and/or the future network 312 (Block 374) may be predicted. Physical facilities are allocated based on the cellular identifier 110 (Block 376).

FIG. 36 is a schematic illustrating still more exemplary embodiments. FIG. 36 is a more detailed diagram illustrating a processor-controlled device 400. As earlier paragraphs explained, exemplary embodiments may partially or entirely operate in any mobile or stationary processor-controlled device. FIG. 36 , then, illustrates the security algorithm 122 stored in a memory subsystem of the processor-controlled device 400. One or more processors communicate with the memory subsystem and execute either, some, or all applications. Because the processor-controlled device 400 is well known to those of ordinary skill in the art, no further explanation is needed.

FIG. 37 depicts other possible operating environments for additional aspects of the exemplary embodiments. FIG. 37 illustrates the security algorithm 122 operating within various other processor-controlled devices 400. FIG. 37 , for example, illustrates that the security algorithm 122 may entirely or partially operate within a set-top box (“STB”) (402), a personal/digital video recorder (PVR/DVR) 404, a Global Positioning System (GPS) device 408, an interactive television 410, a tablet computer 412, or any computer system, communications device, or processor-controlled device utilizing the processor and/or a digital signal processor (DP/DSP) 414. The device 400 may also include watches, radios, vehicle electronics, clocks, printers, gateways, mobile/implantable medical devices, and other apparatuses and systems. Because the architecture and operating principles of the various devices 400 are well known, the hardware and software componentry of the various devices 400 are not further shown and described.

Exemplary embodiments may be physically embodied on or in a computer-readable storage medium. This computer-readable medium, for example, may include CD-ROM, DVD, tape, cassette, floppy disk, optical disk, memory card, memory drive, and large-capacity disks. This computer-readable medium, or media, could be distributed to end-subscribers, licensees, and assignees. A computer program product comprises processor-executable instructions for automatic secure access, as the above paragraphs explained.

While the exemplary embodiments have been described with respect to various features, aspects, and embodiments, those skilled and unskilled in the art will recognize the exemplary embodiments are not so limited. Other variations, modifications, and alternative embodiments may be made without departing from the spirit and scope of the exemplary embodiments. 

The invention claimed is:
 1. A method, comprising: receiving, by a processing system including a processor, an identifier associated with a wireless device; monitoring, by the processing system, network access permissions requested by a wireless device en route to a destination via a plurality of wireless waypoints, wherein the destination is served by a destination network; in response to any of the network access permissions matching the destination network, unlocking, by the processing system, an electronic lock associated with the destination network; and in response to any of the network access permissions failing to match the destination network, generating, by the processing system, a security notification indicating the wireless device has strayed from the plurality of wireless waypoints to the destination network.
 2. The method of claim 1, further comprising receiving, by the processing system, an access notification specifying at least one of the wireless waypoints.
 3. The method of claim 1, further comprising determining, by the processing system, a user associated with the wireless device.
 4. The method of claim 1, further comprising determining, by the processing system, a date associated with the destination network.
 5. The method of claim 1, further comprising determining, by the processing system, a time associated with the destination network.
 6. The method of claim 1, further comprising determining by the processing system, a calendar associated with the wireless device.
 7. The method of claim 1, further comprising sending, by the processing system, a notification associated with the destination network.
 8. A system, comprising: a processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations, the operations comprising: monitoring network access permissions requested by a wireless device traveling to a destination via a plurality of wireless waypoints, wherein the destination is served by a destination network; in response to any of the network access permissions corresponding to the destination network, unlocking an electronic lock that is associated with the destination network; and in response to any of the network access permissions failing to correspond to the destination network, generating a notification indicating the wireless device has strayed from the wireless waypoints to the destination network.
 9. The system of claim 8, wherein the operations further comprise: identifying service set identifiers corresponding to the wireless waypoints; and receiving a request to access a wireless network associated with one of the service set identifiers.
 10. The system of claim 8, wherein the operations further comprise determining a user associated with the wireless device.
 11. The system of claim 8, wherein the operations further comprise determining a date associated with the destination network.
 12. The system of claim 8, wherein the operations further comprise determining a time associated with the destination network.
 13. The system of claim 8, wherein the operations further comprise determining a calendar associated with the wireless device.
 14. The system of claim 8, wherein the operations further comprise sending an instruction to the electronic lock associated with the destination.
 15. A non-transitory, machine-readable storage medium comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations, the operations comprising: monitoring network access permissions requested by a wireless device that travels to a destination along a path comprising a plurality of wireless waypoints, wherein the destination is served by a destination network; in response to any of the network access permissions corresponding to the destination network, providing an unlock instruction to an electronic lock associated with the destination network that instructs the instruction causing the electronic lock to unlock and to permit physical access to an area served by the destination network; and in response to any of the network access permissions failing to match the destination network, providing a security notification indicating the wireless device has strayed from the wireless waypoints to the destination network.
 16. The non-transitory, machine-readable storage medium of claim 15, wherein the operations further comprise: identifying service set identifiers corresponding to the wireless waypoints; and receiving a request to access a wireless network associated with one of the service set identifiers.
 17. The non-transitory, machine-readable storage medium of claim 15, wherein the operations further comprise determining a user associated with the wireless device.
 18. The non-transitory, machine-readable storage medium of claim 15, wherein the operations further comprise determining a date associated with the destination network.
 19. The non-transitory, machine-readable storage medium of claim 15, wherein the operations further comprise determining a time associated with the destination network.
 20. The non-transitory, machine-readable storage medium of claim 15, wherein the operations further comprise determining a calendar associated with the wireless device. 